RailPush MCP Server

218 MCP tools for deploying and managing cloud infrastructure
Connect Claude, Cursor, Windsurf, or any MCP client to a full PaaS platform.

What can your agent do?

With 218 tools, your AI agent gets full control of cloud infrastructure:

Quick start

Hosted server (recommended)

No installation needed. Connect directly:

{
  "mcpServers": {
    "railpush": {
      "url": "https://mcp.railpush.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Claude Code CLI:

claude mcp add railpush --url https://mcp.railpush.com/mcp --header "Authorization: Bearer YOUR_API_KEY"

Cursor: Settings → MCP → Add Server → paste the JSON above.

Local stdio server

For air-gapped or custom setups:

cd mcp && npm install && npm run build

{
  "mcpServers": {
    "railpush": {
      "command": "node",
      "args": ["/path/to/mcp/build/index.js"],
      "env": {
        "RAILPUSH_API_KEY": "your-api-key",
        "RAILPUSH_API_URL": "https://railpush.com"
      }
    }
  }
}

Example: deploy a full-stack app

Tell your agent:

"Create a Node.js web service called 'my-api' on the starter plan, add a PostgreSQL database, set DATABASE_URL as an env var, and deploy from my GitHub repo."

The agent will call:

1. create_service → provisions the service
2. create_database → provisions PostgreSQL
3. reveal_database_credentials → gets the connection string
4. set_env_var → sets DATABASE_URL
5. trigger_deploy → builds and deploys from Git

All in one conversation. No YAML, no CLI, no dashboard clicking.

Transports

Authentication

All requests require an API key. Get one from the RailPush dashboard → Settings → API Keys.

Pass it as:

• Authorization: Bearer YOUR_API_KEY header (hosted server)
• RAILPUSH_API_KEY environment variable (local stdio)

Links

• 🌐 RailPush — the platform
• 📖 Documentation — full docs
• 💰 Pricing — free tier available
• 📋 Changelog — what's new